Search results for "Requirements management"
showing 10 items of 14 documents
An Information Systems Design Product Theory for Integrated Requirements, Test and Defect Management Systems
2012
Software companies need to develop high-quality products fast and with low cost. Development activities are typically distributed in different places and involve multiple stakeholders in different countries. Testing is an important way to ensure product quality but it is costly and takes ample time and resources. Sourcing testing services from specialized service providers is often the most viable option for software businesses. Flexible and effective test process management is especially vital to support the testing life-cycle when external testing service providers are involved. Yet, the extant literature provides little theoretical guidance for managing the testing life-cycle, including …
Understanding flow experience from users’ requirements
2015
This paper argues that the concept of flow can be useful in gaining a better understanding of information system users’ flow experience. This paper applies this concept in the requirements development phase of an Internet protocol television e-learning service development project. The findings show that flow experience can be visualised and measured, and that there are differences in how users see and perceive different features. Some features are driven by more experiential needs, whereas others are driven by more task-oriented goals. The findings indicate that the users’ perceived flow experiences can already be measured during the early phases of information systems IS development projec…
Components of software development risk: how to address them? A project manager survey
2000
Software risk management can be defined as an attempt to formalize risk oriented correlates of development success into a readily applicable set of principles and practices. By using a survey instrument we investigate this claim further. The investigation addresses the following questions: 1) What are the components of software development risk? 2) how does risk management mitigate risk components, and 3) what environmental factors if any influence them? Using principal component analysis we identify six software risk components: 1) scheduling and timing risks, 2) functionality risks, 3) subcontracting risks, 4) requirements management, 5) resource usage and performance risks, and 6) person…
An information systems design product theory for the class of integrated requirements and release management systems
2010
High-tech companies conducting product development need to collect and analyze requirements effectively, plan and implement releases, and allocate requirements to appropriate releases. Requirements and release management are complicated because development activities typically are scattered across multiple sites, involve multiple partners in different countries, leverage various development methods and tools, and are realized through various organizational arrangements such as release projects in organizations structured around products and permanent release teams in organizations responsible for the long-term development and maintenance of strategic software and hardware assets. Flexible, …
Groupware Support for Requirements Management in New Product Development
2005
Large high-technology companies operate in fiercely competitive international markets. To succeed, they need to shorten the cycle time of new product development (NPD) while improving product quality and maintaining or reducing the total resources required. Their abilities to meet these business goals depend on how extensively and effectively they collect, analyze, and utilize requirements in their product development. Creating and sharing such knowledge is complicated partly because the NPD activities of large companies are geographically distributed. Groupware technologies allow knowledge to be created and shared more effectively. Thus, they hold considerable potential as means of meeting…
Prosessin kehittämisen rooli julkisen hallinnon IT-hankkeessa : näkökulmana lainsäädäntöprosessi
2015
Tutkielmassa tarkastelen prosessin kehittämistä lainsäädäntöprosessin ja julkisen hallinnon tietotekniikan (IT:n) uudistamisen näkökulmista. Tutkielmassa yhdistyvät toimintaprosessien kehittämisen ja sähköisen julkisen hallinnon tieteellisen tutkimisen näkökulmat. Tarkastelen lainsäädäntöprosessin kehittämistä osana julkisen hallinnon arkkitehtuurikehyksen mukaista toiminta-arkkitehtuuria. Tutkielma on kirjallisuuskatsaus lainsäädäntöprosessin ja sen tietojärjestelmätuen kehittämiseen liittyvään tietojärjestelmätieteen tutkimukseen. Esitän tutkielmassa tuloksia myös liiketaloustieteen ja oikeusinformatiikan ja -lingvistiikan tutkimuksista. Pyrin hyödyntämään aihepiiriin liittyvää laadullist…
Allowing End-Users to Actively Participate within the Elicitation of Pervasive System Requirements through Immediate Visualization
2009
Efficient requirements engineering activities are essential in order to develop software systems that properly satisfy end-user needs. End-users lack knowledge about requirements engineering techniques or computation in general, and it is very important that they actively participate in the requirements elicitation process because they are the "owners" of the problem. In this paper, we present a tool-supported requirements elicitation technique that is centered on end-users and that allows them to describe the main characteristics of pervasive systems. In addition, we provide end-users with an immediate natural visualization of the described requirements. Furthermore, we present a requireme…
The effect of culture on requirements: a value-based view of prioritization
2015
This paper examines how culture affects requirements and their prioritization. We analyze the requirements of a mobile service, which were collected from Helsinki, Hong Kong, and Las Vegas. We argue that the current prioritization techniques for requirements do not sufficiently account for the cultural effects, nor does the literature offer information on ways of prioritizing such requirements according to users’ values. We see this as problematic because the literature suggests that culture should be viewed as a set of values. Our findings support the argument that we should use a value-based approach in prioritizing requirements. Furthermore, by focusing on the links between needs and val…
Managing and prioritizing requirements risks in information systems development
2018
Tietojärjestelmien suunnittelussa ja toteutuksessa järjestelmän tavoite ja ominaisuudet kuvataan tietojärjestelmän vaatimuksina. Tietojärjestelmävaatimusten keräämisen, kehittämisen ja hallinnan prosessit tietojärjestelmien kehityksessä tähtäävät siihen, että järjestelmän vaatimukset saadaan koottua sidosryhmiltä, ne analysoidaan huolellisesti ja ilmaistaan vaatimukset järjestelmän kehittäjille asianmukaisessa muodossa. Tämä menettely mahdollistaa käyttötarkoitusta vastaava järjestelmän toteuttamisen. Tämän päivän tietojärjestelmäkehityksessä erilaisten ketterien kehitysmallien merkitys on kasvanut, ja voidaankin perustellusti väittää, että erilaiset ketterien menetelmien sovellutukset ovat…
Continuous Requirements Risk Profiling in Information Systems Development
2015
With the increasing adoption of agile, lean, and iterative development methods, information systems development (ISD) has become continuous, meaning that system development moves rapidly from release to release. This means that work practices and challenges that practitioners face have changed. Despite these changes, requirements development is still critical in ISD. However, IS literature is silent on how to manage requirements-related risks in the practice of continuous IS development. To fill this gap, we propose a continuous requirements risk profiling method. The study is informed by design science research methodology, and we apply focus group interviews and a Delphi study for data co…